Suspect links for parent / child

Obj a is linked to obj b - obj b has children objects, object c,d,e....

if obj c changes, can the parent, obj b send a notice to object a about the change to obj c.

They have test plans that link to many reqs - obj a is the test plan and obj b is the heading of many requirements, where the individual requirements are obj c - they do not want to go thru and link the single test plan to every requirement - obj a to obj c - but would like to just have a single link to obj b from obj a - but still get notified when the requirements (obj c) get changed.

Hope that is clear - any advice or help would be great!
sammyc - Fri Apr 17 09:27:01 EDT 2009

Re: Suspect links for parent / child
Tony_Goodman - Mon Apr 20 03:02:55 EDT 2009

Yuk.

Why do people insist on having parent and child requirements in the hierarchy. DOORS does not support this very well and you are relying on the position of an object to have meaning, like it might have in a printed document.

I always recommend that all text objects (i.e. the requirements) are leaf objects (no children).

To answer your question, you will need lots of module specific DXL to create a smoke-and-mirrors type traceability. This will cause nothing but pain in the future when the project team changes an no one can remember why it was done like that.

Tell your guys to link all the requirements to the tests that validate them. Then you can use all the suspect link functionality of DOORS straight out of the box.

Creating the links using some DXL would be very simple and need only be done once.

Re: Suspect links for parent / child
Dinio - Mon Dec 14 08:48:06 EST 2015

Tony_Goodman - Mon Apr 20 03:02:55 EDT 2009
Yuk.

Why do people insist on having parent and child requirements in the hierarchy. DOORS does not support this very well and you are relying on the position of an object to have meaning, like it might have in a printed document.

I always recommend that all text objects (i.e. the requirements) are leaf objects (no children).

To answer your question, you will need lots of module specific DXL to create a smoke-and-mirrors type traceability. This will cause nothing but pain in the future when the project team changes an no one can remember why it was done like that.

Tell your guys to link all the requirements to the tests that validate them. Then you can use all the suspect link functionality of DOORS straight out of the box.

Creating the links using some DXL would be very simple and need only be done once.

So in terms of Doors when say parent of requirement:

1.2.3 Text heading

we do not understand 1.2 in all cases but the requirement which is linked as parent of the 1.2.3?

But what happens if there are not requirements' links in one requirement does it means that it does no have parent?